Update Homebrew formula to CodeTruss CLI v0.2.37 - #5
Merged
Conversation
The tap served 0.2.36 while the website and the newest attested release served 0.2.37. url and sha256 come from the immutable v0.2.37 GitHub release, not the website copy. Verified they are the same bytes: the downloaded release asset, the archive on codetruss.com (both `codetruss-cli-latest.tgz` and the versioned `codetruss-cli-0.2.37.tgz`), and a rebuild from the tagged source in CI all hash to 082a03fe5dd2d9c516acc76504e0bb45bc7d3b5a1fa7308fb2d627ce07a3c627. `gh attestation verify` binds that digest to release.yml at refs/tags/v0.2.37, tag commit f420be17b5b886fb54b4901afb929665c0549ba3, on a GitHub-hosted runner (exit 0 with --signer-workflow, --source-ref, --source-digest and --deny-self-hosted-runners all pinned). The verifier was falsification-checked rather than trusted: a flipped byte, a wrong source-ref, a wrong source-digest, a wrong signer workflow and a wrong repository each exit 1, with exit codes captured directly rather than through a pipeline. The workflow's post-install assertion is version-pinned, so it moves with the formula. Leaving it at 0.2.36 would have failed the install test on both macOS legs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe Homebrew formula now installs Codetruss CLI 0.2.37 with its updated checksum. The workflow verifies the same version. ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The tap served 0.2.36 while codetruss.com and the newest attested GitHub release served 0.2.37.
Formula/codetruss.rb— url and sha256 to the immutable v0.2.37 release asset.github/workflows/test.yml— the post-install assertion is version-pinned, so it moves with the formula. Left at 0.2.36 it would fail the install test on both macOS legs.The digest, and where it came from
Same bytes on every channel, checked with
cmp(exit 0), not by eyeballing hashes:releases/download/v0.2.37/codetruss-cli-0.2.37.tgz082a03fe…codetruss.com/downloads/codetruss-cli-0.2.37.tgz082a03fe…,cmpexit 0codetruss.com/downloads/codetruss-cli-latest.tgz082a03fe…,cmpexit 0082a03fe…Provenance
gh attestation verifybinds that digest torelease.ymlatrefs/tags/v0.2.37, tag commitf420be17b5b886fb54b4901afb929665c0549ba3, on a GitHub-hosted runner — exit 0 with--signer-workflow,--source-ref,--source-digestand--deny-self-hosted-runnersall pinned. Release run 31158510262.Three predicates are bound to it, all in-toto Statement v1:
https://slsa.dev/provenance/v1,https://cyclonedx.org/bom, andhttps://in-toto.io/attestation/release/v0.2.The verifier was falsification-checked, not trusted
Exit codes captured directly. Piping
gh attestation verifyintoheadand reading$?gives head's status — the same known-bad input reads as exit 0 through a pipe and exit 1 under direct capture, which was demonstrated rather than assumed.HTTP 404 ... /attestations/sha256:1f555eec…--source-ref refs/tags/v0.2.36expected SourceRepositoryRef to be refs/tags/v0.2.36, got refs/tags/v0.2.37--source-digest ed7debb…(the 0.2.36 commit)expected SourceRepositoryDigest to be ed7debb…, got f420be17…--signer-workflow …/ci.yml--repo DeliriumPulse/homebrew-codetrussVerify locally
v0.2.36 is untouched: its tag, release, assets and attestations still verify (exit 0 with the 0.2.36 ref and digest pinned).
Summary by CodeRabbit